2015-10-27 - 22442 - Spec - No Email Upon PO conversion #purchaserequisitions #ReleaseProcedure
SPECIFICATIONS
22442 - Spec - No Email Upon PO conversion
Purpose
No Email Upon PO conversion
Admin Info
Purpose
|
No Email Upon PO conversion
|
Requested By
|
Jeff/ Bhumi
|
Spec Created By
|
Laxman
|
Spec Created Date
|
10/27/2015
|
Spec QA by
|
Laxman
|
Objects
|
Z_FM_PO_CONV_NOTIF
ZXM06U44
|
Document Status
|
Complete
|
Estimates
Sl.No
|
Activity
|
Estimation in Hours
|
1
|
Research
|
|
2
|
Documentation
|
04
|
3
|
Development/ Config
|
12
|
4
|
Unit test in DEV
|
08
|
5
|
Unit test in QUA
|
04
|
6
|
Other activity
|
|
|
TOTAL
|
28
|
References
Prior Tickets
[Provide links of prior associated Spec / Break Fix BOSS document(s)]
Documents
[Attach any document(s) received for the requirement(s)]
Spec Changes
[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]
Sl.
|
Change Details
|
Requested By
|
Requested On
|
Notes if any
|
|
|
|
|
|
Functional Requirement
Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]
While converting the below given purchase requisition to purchase order email notification is not triggered.
Example: PO 4500142855, requisition 16761237
In Scope:
[List the
activities to be included in scope]
Out of Scope:
[Out of scope activities]
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
This issue is due to creation of purchase requisitions with different account assignments (X & K). For MRO purchase requisitions account assignment should be ‘K’. So while converting PR to PO email will be triggered if account assignment of first item is ‘K’. But for the given purchase requisition account assignment of first item is X not K. So email notification is not triggered.
At the time of initial design of PR release strategy during discussions understand that MRO purchase requisitions (with account assignment ‘k’) are not combined with others. But now users want to combine different account assignments like K and X. To handle this situation as advised by New Era modified the logic to trigger the email based on material group instead of account assignment. As per this new logic email will be triggered after PR to PO conversion if material group of first line item is 06.
Test Plan
[List test scenarios/cases to be executed here]
Test ID
|
Test Scenario
|
Expected Results
|
MM001
|
Create the purchase requisition with material group (06) for first line item and convert that PR into PO after release
|
Email notification after PR to PO conversion
|
MM002
|
Create the purchase requisition with material group (06) for first line item and account assignment for first line item should be X and
for second line item K. Then convert that PR into PO after release
|
Email notification after PR to PO conversion
|
Solution Details
[Provide complete technical details for configuration or programming here]
Modified the logic to trigger the email notification based material group.
Issues
[List Issues / Bugs identified in configuration or development]